home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c
- Subject: Re: Borland Turbo C
- Date: 31 Jan 1996 06:53:34 -0800
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4envpeINN29h@keats.ugrad.cs.ubc.ca>
- References: <4dlo30$juu@lugb.latrobe.edu.au> <8B994AE.02C7001C6C.uuout@sourcebbs.com>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <8B994AE.02C7001C6C.uuout@sourcebbs.com>,
- DAVID MOHORN <david.mohorn@sourcebbs.com> wrote:
- >
- >CN>Is there such a thing as a version of Borland Turbo C which is bug free or
- > >is Borland just friggin useless? I am getting compile time errors in the
- > >supplied header files. Any one else come across this problem?
- >
- >Most of the time when someone complains about a compiler being broken,
- >its usually their code! You obviously don't know what you're doing.
- >Care to post a fragment of the code in question?
-
- Borland C is broken. The programmer who is doing the Windows portion of a
- project I'm working on has discovered that Borland doesn't even pass arguments
- properly. Like if you pass "int" arguments to a function that is
- *ANSI prototyped* as having long arguments, it will not do the conversion, and
- just bang a bunch of 16-bit words on the stack. He had to declare temporary
- long variables, assign the values into these and then do the call.
-
- Duh!
-
- Borland's 32-bit compiler also has the worst optimization in the business,
- way behind Microsoft C, Watcom, UNIXWare cc, and probably a host of others.
- --
-
-